Systems and methods for building management system sensor diagnostics and management

ABSTRACT

A system for managing sensors of a building includes a data repository configured to store sensor data from the sensors, a building management system (BMS) controller configured to monitor or control components of the building based on sensor data provided by the sensors, and a sensor diagnostic system. The sensor diagnostic system is configured to receive samples of the sensor data from the sensors, classify each of the samples of the sensor data as faulty or non-faulty, generate supplemental data based on a subset of the samples of the sensor data that are classified as faulty and corresponding attributes of the subset of the samples of the sensor data that are classified as faulty, and provide the supplemental data to the BMS controller to monitor or control the components of the building based on the supplemental data.

CROSS-REFERENCE TO RELATED PATENT APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/294,268 filed Mar. 6, 2019, the entire disclosure of which isincorporated by reference herein.

BACKGROUND

The present disclosure relates generally to a building management systemand more particularly to fault detection systems in buildings. Thepresent disclosure relates specifically to a fault detection systemwhich intelligently supplements sensor data.

A building typically includes various building subsystems. Examples ofsuch building subsystems include, for instance, an HVAC subsystem, asecurity subsystem, a lighting subsystem, and so forth. Each of thebuilding subsystems may include a number of device(s) for controllingvarious aspects of the respective building subsystem.

Occasionally, sensors in various building subsystems may experiencefaults. As a result of sensor faults, the corresponding sensors mayprovide inconsistent data. Both the inconsistent data and the time toreplace such sensors may result in downtime.

SUMMARY

One implementation of the present disclosure is a sensor managementsystem. The sensor management system includes a historical datarepository configured to store historical data from a plurality ofsensors. The historical data comprising one or more attributes definingone or more characteristics related to the capture of the historicaldata. The sensor management system includes a building management system(BMS) controller configured to control one or more components of abuilding subsystem based on data provided by one or more sensors. Thesensor management system includes a sensor diagnostic systemcommunicably coupled to a sensor of a building subsystem, the historicaldata repository, and the BMS controller. The sensor diagnostic systemincludes a processing circuit including a processor and memory. Thememory stores instructions that, when executed by the processor, causethe processor to perform operations. The operations include receiving,from a sensor of the one or more sensors, sensor data. The operationsinclude determining, based on the sensor data, at least one fault in thesensor data. The operations include selecting, from the data repository,substitute sensor data for the sensor. The substitute sensor data isselecting based on a comparison of one or more attributes of the sensordata and the one or more attributes of the historical data in the datarepository. The operations include providing, in replacement of thesensor data from the sensor, the substitute sensor data to the BMScontroller.

In some embodiments, the operations further include deactivating thesensor responsive to determining that the sensor data includes at leastone fault.

In some embodiments, providing the supplemental sensor data includesidentifying a sample rate for the sensor, and providing, in replacementof the sensor data from the sensor, the substitute sensor data to theBMS controller at the identified sample rate.

In some embodiments, the operations further include receiving, from anoperator client device, a disable signal. The operations may furtherinclude disabling the providing of the supplemental data to the BMScontroller.

In some embodiments, the at least one attribute of the historical sensordata is at least a portion of a timestamp indicating a day and month inwhich the historical sensor data is captured.

In some embodiments, the historical sensor data was captured at least ayear prior to the sensor data being captured by the sensor.

In some embodiments, the at least one attribute of the historical sensordata is metadata which indicates a service space, and wherein the sensorservices the service space

Another implementation of the present disclosure includes a sensordiagnostic system communicably coupled to a sensor of a buildingsubsystem, a historical data repository and a building management system(BMS) controller. The historical data repository is configured to storehistorical data from a plurality of sensors. The historical datacomprising one or more attributes defining one or more characteristicsrelated to the capture of the historical data. The BMS controllerconfigured to control one or more components of a building subsystembased on data provided by one or more sensors. The sensor diagnosticsystem includes a processing circuit including a processor and memory.The memory stores instructions that, when executed by the processor,cause the processor to perform operations. The operations includereceiving, from a sensor of the one or more sensors, sensor data. Theoperations include determining, based on the sensor data, at least onefault in the sensor data. The operations include selecting, from thedata repository, substitute sensor data for the sensor. The substitutesensor data is selecting based on a comparison of one or more attributesof the sensor data and the one or more attributes of the historical datain the data repository. The operations include providing, in replacementof the sensor data from the sensor, the substitute sensor data to theBMS controller.

In some embodiments, providing the supplemental sensor data includesidentifying a sample rate for the sensor, and providing, in replacementof the sensor data from the sensor, the supplemental sensor data to theBMS controller at the identified sample rate.

In some embodiments, the operations further include receiving, from anoperator client device, a disable signal. The operations may furtherinclude disabling the providing of the supplemental data to the BMScontroller.

In some embodiments, the disable signal is received responsive to thesensor being replaced with a replacement sensor. The operations mayfurther include providing, to the BMS controller, sensor data from thereplacement sensor.

In some embodiments, the at least one attribute of the historical sensordata is at least a portion of a timestamp indicating a day and month inwhich the historical sensor data is captured.

In some embodiments, the historical sensor data was captured at least ayear prior to the sensor data being captured by the sensor.

In some embodiments, the at least one attribute of the historical sensordata is metadata which indicates a service space, and wherein the sensorservicing the service space.

Another implementation of the present disclosure includes a method ofmanaging sensor data. The method includes receiving, from a sensor of abuilding subsystem servicing a space in a building, sensor data. Themethod includes determining, based on the sensor data, a presence offaulty sensor data. The method includes selecting, from a historicaldata repository configured to store historical data from a plurality ofsensors which includes one or more attributes defining, substitutesensor data for the sensor. The substitute sensor data is selectingbased on a comparison of one or more attributes of the faulty sensordata and the one or more attributes of the historical data in the datarepository. The method includes providing, in replacement of the sensordata from the sensor, the substitute sensor data to a BMS controllerconfigured to control one or more components of the building subsystem.

In some embodiments, the method further includes deactivating the sensorresponsive to determining that the sensor data is faulty.

In some embodiments, providing the supplemental sensor data includesidentifying a sample rate for the sensor, and providing, in replacementof the sensor data from the sensor, the supplemental sensor data to theBMS controller at the identified sample rate.

In some embodiments, the method further includes receiving, from anoperator client device, a disable signal. The method may further includedisabling the providing of the supplemental data to the BMS controller.

In some embodiments, the at least one attribute of the historical sensordata is at least a portion of a timestamp indicating a day and month inwhich the historical sensor data is captured.

In some embodiments, the at least one attribute of the historical sensordata is metadata which indicates a service space, and wherein the sensorservices the service space.

Those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the devices and/orprocesses described herein, as defined solely by the claims, will becomeapparent in the detailed description set forth herein and taken inconjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a heating, ventilating,or air conditioning (HVAC) system and a building management system(BMS), according to an exemplary embodiment.

FIG. 2 is a schematic diagram of a waterside system which may be used tosupport the HVAC system of FIG. 1 , according to an exemplaryembodiment.

FIG. 3 is a block diagram of an airside system which may be used as partof the HVAC system of FIG. 1 , according to an exemplary embodiment.

FIG. 4 is a block diagram of a BMS which may be implemented in thebuilding of FIG. 1 , according to an exemplary embodiment.

FIG. 5 is a block diagram of a system for sensor management, accordingto an exemplary embodiment.

FIG. 6 is a flowchart depicting an example method of selectingsubstitute data, according to an exemplary embodiment.

FIG. 7 is an example environment within which the system of FIG. 5 maybe implemented, according to an exemplary embodiment.

FIG. 8 is a flowchart depicting an example method of managing sensordata, according to an exemplary embodiment.

DETAILED DESCRIPTION

Referring generally to the FIGURES, systems and methods for sensordiagnostics and management are shown and described, according to anexemplary embodiment. The systems and methods described herein mayautomatically replace sensor data from sensors experiencing a fault withhistorical sensor data. The systems and methods described herein may bepracticed in any number of environments, buildings, enterprises, etc.

In some implementations of building management solutions, varioussensor(s) may be arranged in a building to monitor, evaluate, orotherwise detect conditions in a respective building subsystem. Thesensor(s) may generate sensor data corresponding to such detectedconditions. In most instances, the sensor data is reliable. However, insome instances (such as those where the sensor(s) are experiencing afault), the sensor data may be unreliable. Where the sensor(s) areexperiencing a fault, the sensor(s) may be replaced or fixed so as toalleviate the unreliable sensor data. As a result, the building and/orbuilding subsystem may have downtime while the sensor(s) are replaced orfixed. Such downtime may interrupt business, decrease profits andproductivity, etc. In some embodiments, systems and methods describedherein advantageously automatically detect sensor faults and supplementthe corresponding sensor data to decrease downtime.

According to at least some aspects described herein, a sensor managementsystem includes a historical data repository, a building managementsystem (BMS) controller, and a sensor diagnostics system. The historicaldata repository may be configured to store historical data from aplurality of sensors. The historical data may be recorded under aplurality of conditions. The BMS controller may be configured to controlone or more components of a building subsystem based on data provided byone or more sensors. The sensor diagnostic system may be communicablycoupled to a sensor of a building subsystem, the historical datarepository, and the BMS controller. The sensor diagnostic system mayreceive, from a sensor of the one or more sensors, sensor datacorresponding to a detected condition of the building subsystem. Thesensor diagnostic system may determine, based on the sensor data, thatthe sensor is experiencing a fault. The sensor diagnostic system mayidentify, in the data repository, supplemental sensor data for thesensor. The supplemental sensor data may be identified based on acondition in which the sensor data is received from the sensor. Thesensor diagnostic system may provide, in replacement of the sensor datafrom the sensor, the supplemental sensor data to the BMS controller.

Some embodiments described herein provide a system and method for sensordiagnostics and management. Some embodiments described herein decreasedowntime by automatically detecting faults of sensors and replacingsensor data corresponding to sensors experiencing faults with historicalsensor data. Since the sensor data is replaced with historical sensordata, the sensors are—in effect—taken out of commission (as the sensordata generated thereby is not provided to any systems/components) whilethe building subsystem itself remains operational. Some embodimentsdescribed herein maintain performance/operation characteristics byselecting historical sensor data from the historical data repositorywhich is most similar to expected sensor data from the sensor(s). Someembodiments select the most similar historical sensor data byidentifying sensor data captured under similar conditions as theconditions in which the sensor(s) experiencing a fault captured thecorresponding sensor data. Various other benefits and aspects of thedisclosure are described hereinafter with reference to the FIGURESbelow.

Building Management System and HVAC System

Referring now to FIGS. 1-4 , an exemplary building management system(BMS) and HVAC system in which the systems and methods of the presentdisclosure may be implemented are shown, according to an exemplaryembodiment. Referring particularly to FIG. 1 , a perspective view of abuilding 10 is shown. Building 10 is served by a BMS. A BMS is, ingeneral, a system of devices configured to control, monitor, and manageequipment in or around a building or building area. A BMS may include,for example, an HVAC system, a security system, a lighting system, afire alerting system, any other system that is capable of managingbuilding functions or devices, or any combination thereof.

The BMS that serves building 10 includes an HVAC system 100. HVAC system100 may include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 mayprovide heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 may use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which may be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3 .

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 may use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and may circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 may be located inor around building 10 (as shown in FIG. 1 ) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid may be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 may add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 may place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104may be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow may be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 may transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 may include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid may then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and mayprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 may include dampers or other flow control elements thatmay be operated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 116 orother flow control elements. AHU 106 may include various sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 may receive input from sensorslocated within AHU 106 and/or within the building zone and may adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve set point conditions for the building zone.

Referring now to FIG. 2 , a block diagram of a waterside system 200 isshown, according to an exemplary embodiment. In various embodiments,waterside system 200 may supplement or replace waterside system 120 inHVAC system 100 or may be implemented separate from HVAC system 100.When implemented in HVAC system 100, waterside system 200 may include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and may operate to supply a heated or chilledfluid to AHU 106. The HVAC devices of waterside system 200 may belocated within building 10 (e.g., as components of waterside system 120)or at an offsite location such as a central plant.

In FIG. 2 , waterside system 200 is shown as a central plant having aplurality of subplants 202-212. Subplants 202-212 are shown to include aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve the thermal energy loads(e.g., hot water, cold water, heating, cooling, etc.) of a building orcampus. For example, heater subplant 202 may be configured to heat waterin a hot water loop 214 that circulates the hot water between heatersubplant 202 and building 10. Chiller subplant 206 may be configured tochill water in a cold water loop 216 that circulates the cold waterbetween chiller subplant 206 and building 10. Heat recovery chillersubplant 204 may be configured to transfer heat from cold water loop 216to hot water loop 214 to provide additional heating for the hot waterand additional cooling for the cold water. Condenser water loop 218 mayabsorb heat from the cold water in chiller subplant 206 and reject theabsorbed heat in cooling tower subplant 208 or transfer the absorbedheat to hot water loop 214. Hot TES subplant 210 and cold TES subplant212 may store hot and cold thermal energy, respectively, for subsequentuse.

Hot water loop 214 and cold water loop 216 may deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air may bedelivered to individual zones of building 10 to serve the thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) may be used inplace of or in addition to water to serve the thermal energy loads. Inother embodiments, subplants 202-212 may provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 200are within the teachings of the present disclosure.

Each of subplants 202-212 may include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 202 is shown to include a plurality of heating elements 220(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 214. Heater subplant 202 is also shown toinclude several pumps 222 and 224 configured to circulate the hot waterin hot water loop 214 and to control the flow rate of the hot waterthrough individual heating elements 220. Chiller subplant 206 is shownto include a plurality of chillers 232 configured to remove heat fromthe cold water in cold water loop 216. Chiller subplant 206 is alsoshown to include several pumps 234 and 236 configured to circulate thecold water in cold water loop 216 and to control the flow rate of thecold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality ofheat recovery heat exchangers 226 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 216 to hot water loop214. Heat recovery chiller subplant 204 is also shown to include severalpumps 228 and 230 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 226 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 238 configured to remove heat from the condenser water incondenser water loop 218. Cooling tower subplant 208 is also shown toinclude several pumps 240 configured to circulate the condenser water incondenser water loop 218 and to control the flow rate of the condenserwater through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configuredto store the hot water for later use. Hot TES subplant 210 may alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 242. Cold TES subplant 212is shown to include cold TES tanks 244 configured to store the coldwater for later use. Cold TES subplant 212 may also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines inwaterside system 200 include an isolation valve associated therewith.Isolation valves may be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 200. In various embodiments, waterside system 200 may includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 200 and the types of loadsserved by waterside system 200.

Referring now to FIG. 3 , a block diagram of an airside system 300 isshown, according to an exemplary embodiment. In various embodiments,airside system 300 may supplement or replace airside system 130 in HVACsystem 100 or may be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, airside system 300 may include a subsetof the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116,ducts 112-114, fans, dampers, etc.) and may be located in or aroundbuilding 10. Airside system 300 may operate to heat or cool an airflowprovided to building 10 using a heated or chilled fluid provided bywaterside system 200.

In FIG. 3 , airside system 300 is shown to include an economizer-typeAHU 302. Economizer-type AHUs vary the amount of outside air and returnair used by the air handling unit for heating or cooling. For example,AHU 302 may receive return air 304 from building zone 306 via return airduct 308 and may deliver supply air 310 to building zone 306 via supplyair duct 312. In some embodiments, AHU 302 is a rooftop unit located onthe roof of building 10 (e.g., AHU 106 as shown in FIG. 1 ) or otherwisepositioned to receive both return air 304 and outside air 314. AHU 302may be configured to operate exhaust air damper 316, mixing damper 318,and outside air damper 320 to control an amount of outside air 314 andreturn air 304 that combine to form supply air 310. Any return air 304that does not pass through mixing damper 318 may be exhausted from AHU302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 may be operated by an actuator. For example,exhaust air damper 316 may be operated by actuator 324, mixing damper318 may be operated by actuator 326, and outside air damper 320 may beoperated by actuator 328. Actuators 324-328 may communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 mayreceive control signals from AHU controller 330 and may provide feedbacksignals to AHU controller 330. Feedback signals may include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat may be collected, stored, or used by actuators 324-328. AHUcontroller 330 may be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3 , AHU 302 is shown to include a cooling coil334, a heating coil 336, and a fan 338 positioned within supply air duct312. Fan 338 may be configured to force supply air 310 through coolingcoil 334 and/or heating coil 336 and provide supply air 310 to buildingzone 306. AHU controller 330 may communicate with fan 338 viacommunications link 340 to control a flow rate of supply air 310. Insome embodiments, AHU controller 330 controls an amount of heating orcooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and may return thechilled fluid to waterside system 200 via piping 344. Valve 346 may bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that may beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 may receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and may return the heatedfluid to waterside system 200 via piping 350. Valve 352 may bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that may be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 may be controlled by an actuator. Forexample, valve 346 may be controlled by actuator 354 and valve 352 maybe controlled by actuator 356. Actuators 354-356 may communicate withAHU controller 330 via communications links 358-360. Actuators 354-356may receive control signals from AHU controller 330 and may providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 may also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a setpoint temperature for supplyair 310 or to maintain the temperature of supply air 310 within asetpoint temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU controller 330may control the temperature of supply air 310 and/or building zone 306by activating or deactivating coils 334-336, adjusting a speed of fan338, or a combination of both.

Still referring to FIG. 3 , airside system 300 is shown to include a BMScontroller 366 and a client device 368. BMS controller 366 may includeone or more computer systems (e.g., servers, supervisory controllers,subsystem controllers, etc.) that serve as system-level controllers,application or data servers, head nodes, or master controllers forairside system 300, waterside system 200, HVAC system 100, and/or othercontrollable systems that serve building 10. BMS controller 366 maycommunicate with multiple downstream building systems or subsystems(e.g., HVAC system 100, a security system, a lighting system, watersidesystem 200, etc.) via a communications link 370 according to like ordisparate protocols (e.g., LON, BACnet, etc.). In various embodiments,AHU controller 330 and BMS controller 366 may be separate (as shown inFIG. 3 ) or integrated. In an integrated implementation, AHU controller330 may be a software module configured for execution by a processor ofBMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, setpoints, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 may provide BMScontroller 366 with temperature measurements from temperature sensors362-364, equipment on/off states, equipment operating capacities, and/orany other information that may be used by BMS controller 366 to monitoror control a variable state or condition within building zone 306.

Client device 368 may include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 may be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 may be a stationary terminal or amobile device. For example, client device 368 may be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 may communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Referring now to FIG. 4 , a block diagram of a BMS 400 is shown,according to an exemplary embodiment. BMS 400 may be implemented inbuilding 10 to automatically monitor and control various buildingfunctions. BMS 400 is shown to include BMS controller 366 and aplurality of building subsystems 428. Building subsystems 428 are shownto include a building electrical subsystem 434, an informationcommunication technology (ICT) subsystem 436, a security subsystem 438,an HVAC subsystem 440, a lighting subsystem 442, a lift/escalatorssubsystem 432, and a fire safety subsystem 430. In various embodiments,building subsystems 428 may include fewer, additional, or alternativesubsystems. For example, building subsystems 428 may also oralternatively include a refrigeration subsystem, an advertising orsignage subsystem, a cooking subsystem, a vending subsystem, a printeror copy service subsystem, or any other type of building subsystem thatuses controllable equipment and/or sensors to monitor or controlbuilding 10. In some embodiments, building subsystems 428 includewaterside system 200 and/or airside system 300, as described withreference to FIGS. 2-3 .

Each of building subsystems 428 may include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 may include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3. For example, HVAC subsystem 440 may include any number of chillers,heaters, handling units, economizers, field controllers, supervisorycontrollers, actuators, temperature sensors, and/or other devices forcontrolling the temperature, humidity, airflow, or other variableconditions within building 10. Lighting subsystem 442 may include anynumber of light fixtures, ballasts, lighting sensors, dimmers, or otherdevices configured to controllably adjust the amount of light providedto a building space. Security subsystem 438 may include occupancysensors, video surveillance cameras, digital video recorders, videoprocessing servers, intrusion detection devices, access control devicesand servers, or other security-related devices.

Still referring to FIG. 4 , BMS controller 366 is shown to include acommunications interface 407 and a BMS interface 409. Interface 407 mayfacilitate communications between BMS controller 366 and externalapplications (e.g., monitoring and reporting applications 422,enterprise control applications 426, remote systems and applications444, applications residing on client devices 448, etc.) for allowinguser control, monitoring, and adjustment to BMS controller 366 and/orsubsystems 428. Interface 407 may also facilitate communications betweenBMS controller 366 and client devices 448. BMS interface 409 mayfacilitate communications between BMS controller 366 and buildingsubsystems 428 (e.g., HVAC, lighting security, lifts, powerdistribution, business, etc.).

Interfaces 407 and 409 may be or may include wired or wirelesscommunications interfaces (e.g., jacks, antennas, transmitters,receivers, transceivers, wire terminals, etc.) for conducting datacommunications with building subsystems 428 or other external systems ordevices. In various embodiments, communications via interfaces 407 and409 may be direct (e.g., local wired or wireless communications) or viaa communications network 446 (e.g., a WAN, the Internet, a cellularnetwork, etc.). For example, interfaces 407 and 409 may include anEthernet card and port for sending and receiving data via anEthernet-based communications link or network. In another example,interfaces 407 and 409 may include a Wi-Fi transceiver for communicatingvia a wireless communications network. In another example, one or bothof interfaces 407 and 409 may include cellular or mobile phonecommunications transceivers. In one embodiment, communications interface407 is a power line communications interface and BMS interface 409 is anEthernet interface. In other embodiments, both communications interface407 and BMS interface 409 are Ethernet interfaces or are the sameEthernet interface.

Still referring to FIG. 4 , BMS controller 366 is shown to include aprocessing circuit 404 including a processor 406 and memory 408.Processing circuit 404 may be communicably connected to BMS interface409 and/or communications interface 407 such that processing circuit 404and the various components thereof may send and receive data viainterfaces 407 and 409. Processor 406 may be implemented as a generalpurpose processor, an application specific integrated circuit (ASIC),one or more field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents.

Memory 408 (e.g., memory, memory unit, storage device, etc.) may includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers, and modules described in thepresent application. Memory 408 may be or include volatile memory ornon-volatile memory. Memory 408 may include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present application. According to anexemplary embodiment, memory 408 is communicably connected to processor406 via processing circuit 404 and includes computer code for executing(e.g., by processing circuit 404 and/or processor 406) one or moreprocesses described herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various otherembodiments, BMS controller 366 may be distributed across multipleservers or computers (e.g., that may exist in distributed locations).Further, while FIG. 4 shows applications 422 and 426 as existing outsideof BMS controller 366, in some embodiments, applications 422 and 426 maybe hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4 , memory 408 is shown to include an enterpriseintegration layer 410, an automated measurement and validation (AM&V)layer 412, a demand response (DR) layer 414, a fault detection anddiagnostics (FDD) layer 416, an integrated control layer 418, and abuilding subsystem integration later 420. Layers 410-420 may beconfigured to receive inputs from building subsystems 428 and other datasources, determine optimal control actions for building subsystems 428based on the inputs, generate control signals based on the optimalcontrol actions, and provide the generated control signals to buildingsubsystems 428. The following paragraphs describe some of the generalfunctions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 may be configured to serve clients orlocal applications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 may be configured to provide subsystem-spanning controlto a graphical user interface (GUI) or to any number of enterprise-levelbusiness applications (e.g., accounting systems, user identificationsystems, etc.). Enterprise control applications 426 may also oralternatively be configured to provide configuration GUIs forconfiguring BMS controller 366. In yet other embodiments, enterprisecontrol applications 426 may work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 may be configured to managecommunications between BMS controller 366 and building subsystems 428.For example, building subsystem integration layer 420 may receive sensordata and input signals from building subsystems 428 and provide outputdata and control signals to building subsystems 428. Building subsystemintegration layer 420 may also be configured to manage communicationsbetween building subsystems 428. Building subsystem integration layer420 translates communications (e.g., sensor data, input signals, outputsignals, etc.) across a plurality of multi-vendor/multi-protocolsystems.

Demand response layer 414 may be configured to optimize resource usage(e.g., electricity use, natural gas use, water use, etc.) and/or themonetary cost of such resource usage in response to satisfy the demandof building 10. The optimization may be based on time-of-use prices,curtailment signals, energy availability, or other data received fromutility providers, distributed energy generation systems 424, fromenergy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or fromother sources. Demand response layer 414 may receive inputs from otherlayers of BMS controller 366 (e.g., building subsystem integration layer420, integrated control layer 418, etc.). The inputs received from otherlayers may include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs may also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to an exemplary embodiment, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses may include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changingsetpoints, or activating/deactivating building equipment or subsystemsin a controlled manner. Demand response layer 414 may also includecontrol logic configured to determine when to utilize stored energy. Forexample, demand response layer 414 may determine to begin using energyfrom energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control moduleconfigured to actively initiate control actions (e.g., automaticallychanging setpoints) which minimize energy costs based on one or moreinputs representative of or based on demand (e.g., price, a curtailmentsignal, a demand level, etc.). In some embodiments, demand responselayer 414 uses equipment models to determine an optimal set of controlactions. The equipment models may include, for example, thermodynamicmodels describing the inputs, outputs, and/or functions performed byvarious sets of building equipment. Equipment models may representcollections of building equipment (e.g., subplants, chiller arrays,etc.) or individual devices (e.g., individual chillers, heaters, pumps,etc.).

Demand response layer 414 may further include or draw upon one or moredemand response policy definitions (e.g., databases, XML, files, etc.).The policy definitions may be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs may be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions mayspecify which equipment may be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what setpoints may be changed, what the allowable setpoint adjustment range is, how long to hold a high demand setpointbefore returning to a normally scheduled setpoint, how close to approachcapacity limits, which equipment modes to utilize, the energy transferrates (e.g., the maximum rate, an alarm rate, other rate boundaryinformation, etc.) into and out of energy storage devices (e.g., thermalstorage tanks, battery banks, etc.), and when to dispatch on-sitegeneration of energy (e.g., via fuel cells, a motor generator set,etc.).

Integrated control layer 418 may be configured to use the data input oroutput of building subsystem integration layer 420 and/or demandresponse later 414 to make control decisions. Due to the subsystemintegration provided by building subsystem integration layer 420,integrated control layer 418 may integrate control activities of thesubsystems 428 such that the subsystems 428 behave as a singleintegrated supersystem. In an exemplary embodiment, integrated controllayer 418 includes control logic that uses inputs and outputs from aplurality of building subsystems to provide greater comfort and energysavings relative to the comfort and energy savings that separatesubsystems could provide alone. For example, integrated control layer418 may be configured to use an input from a first subsystem to make anenergy-saving control decision for a second subsystem. Results of thesedecisions may be communicated back to building subsystem integrationlayer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 may be configured toenhance the effectiveness of demand response layer 414 by enablingbuilding subsystems 428 and their respective control loops to becontrolled in coordination with demand response layer 414. Thisconfiguration may advantageously reduce disruptive demand responsebehavior relative to conventional systems. For example, integratedcontrol layer 418 may be configured to assure that a demandresponse-driven upward adjustment to the setpoint for chilled watertemperature (or another component that directly or indirectly affectstemperature) does not result in an increase in fan energy (or otherenergy used to cool a space) that would result in greater total buildingenergy use than was saved at the chiller.

Integrated control layer 418 may be configured to provide feedback todemand response layer 414 so that demand response layer 414 checks thatconstraints (e.g., temperature, lighting levels, etc.) are properlymaintained even while demanded load shedding is in progress. Theconstraints may also include setpoint or sensed boundaries relating tosafety, equipment operating limits and performance, comfort, fire codes,electrical codes, energy codes, and the like. Integrated control layer418 is also logically below fault detection and diagnostics layer 416and AM&V layer 412. Integrated control layer 418 may be configured toprovide calculated inputs (e.g., aggregations) to these higher levelsbased on outputs from more than one building subsystem.

AM&V layer 412 may be configured to verify that control strategiescommanded by integrated control layer 418 or demand response layer 414are working properly (e.g., using data aggregated by AM&V layer 412,integrated control layer 418, building subsystem integration layer 420,FDD layer 416, or otherwise). The calculations made by AM&V layer 412may be based on building system energy models and/or equipment modelsfor individual BMS devices or subsystems. For example, AM&V layer 412may compare a model-predicted output with an actual output from buildingsubsystems 428 to determine an accuracy of the model.

FDD layer 416 may be configured to provide on-going fault detection forbuilding subsystems 428, building subsystem devices (i.e., buildingequipment), and control algorithms used by demand response layer 414 andintegrated control layer 418. FDD layer 416 may receive data inputs fromintegrated control layer 418, directly from one or more buildingsubsystems or devices, or from another data source. FDD layer 416 mayautomatically diagnose and respond to detected faults. The responses todetected or diagnosed faults may include providing an alert message to auser, a maintenance scheduling system, or a control algorithm configuredto attempt to repair the fault or to work-around the fault.

FDD layer 416 may be configured to output a specific identification ofthe faulty component or cause of the fault (e.g., loose damper linkage)using detailed subsystem inputs available at building subsystemintegration layer 420. In other exemplary embodiments, FDD layer 416 isconfigured to provide “fault” events to integrated control layer 418which executes control strategies and policies in response to thereceived fault events. According to an exemplary embodiment, FDD layer416 (or a policy executed by an integrated control engine or businessrules engine) may shut-down systems or direct control activities aroundfaulty devices or systems to reduce energy waste, extend equipment life,or assure proper control response.

FDD layer 416 may be configured to store or access a variety ofdifferent system data stores (or data points for live data). FDD layer416 may use some content of the data stores to identify faults at theequipment level (e.g., specific chiller, specific AHU, specific terminalunit, etc.) and other content to identify faults at component orsubsystem levels. For example, building subsystems 428 may generatetemporal (i.e., time-series) data indicating the performance of BMS 400and the various components thereof. The data generated by buildingsubsystems 428 may include measured or calculated values that exhibitstatistical characteristics and provide information about how thecorresponding system or process (e.g., a temperature control process, aflow control process, etc.) is performing in terms of error from itssetpoint. These processes may be examined by FDD layer 416 to exposewhen the system begins to degrade in performance and alert a user torepair the fault before it becomes more severe.

Systems and Methods for Sensor Diagnostics and Management

Referring to FIG. 5 , depicted is a block diagram of a system 500 forsensor management, according to an exemplary embodiment. The system 500is shown to include a sensor diagnostics system 502, a historical datarepository 504, a building 10 (similar to the buildings 10 describedabove with reference to FIG. 1 ), and the BMS controller 366 (similar tothe BMS controller 366 described above with reference to FIG. 3 and FIG.4 ). The building 10 may include a plurality of sensors 506. Thesensor(s) 506 may be components or elements of a respective buildingsubsystem 428. As described in greater detail below, the sensordiagnostics system 502 may be configured to receive the sensor data fromthe sensor(s) 506. The sensor diagnostics system 502 may be configuredto determine whether the sensor(s) 506 are experiencing a fault based onthe sensor data. The sensor diagnostics system 502 may be configured toselectively provide supplemental sensor data from the historical datarepository 504 to the BMS controller 366 based on whether the sensor(s)506 are experiencing a fault.

As described in detail above, the BMS controller 366 may generally beconfigured to control various aspects, devices, components, etc. withinthe various building subsystems 428 (for instance, a fire safetysubsystem 430, lifts/escalators subsystem 432, electrical subsystem 434,ICT subsystem 436, security subsystem 438, HVAC subsystem 440, lightingsubsystem 442, as described with reference to FIG. 4 ). Generallyspeaking, the building subsystem integration layer 420 may be configuredto manage communications between BMS controller 366 and buildingsubsystems 428. The building subsystem integration layer 420 may beconfigured to receive sensor data and input signals from the buildingsubsystems 428 and provide output data and control signals to thebuilding subsystems 428. The building subsystem integration layer 420may translate communications (such as sensor data) across a plurality ofmulti-vendor/multi-protocol systems. The demand response layer 414 maybe configured to receive inputs from various other layers (such as thebuilding subsystem integration layer 420) and implement variousstrategies to satisfy the demand of the building 10. Hence, generallyspeaking, the building subsystem integration layer 420 of the BMScontroller 366 may receive inputs (including sensor data), the demandresponse layer 414 may generate control signals for various buildingcomponents based on the inputs received by the building subsystemintegration layer 420, and the building subsystem integration layer 420may provide the control signals generated by the demand response layer414 to building subsystems 428.

The system 500 is shown to include a sensor diagnostic system 502. Thesensor diagnostic system 502 may be any device(s) or component(s)designed or implemented to identify faults of sensor(s) 506 in thevarious building subsystem(s) 428. The sensor diagnostic system 502 maybe configured to replace sensor data from the sensor(s) 506 experiencinga fault with historical sensor data stored in the historical datarepository 504. The sensor diagnostic system 502 may be configured toprovide the historical sensor data to the BMS controller 366 forcontrolling the building subsystem(s) 428. Hence, in some instances, theBMS controller 366 may control the building subsystem(s) 428 based onsensor data generated by the sensor(s) 506, and, in other instances, theBMS controller 366 may control the building subsystem(s) 428 based atleast in part on historical sensor data. While shown as separate fromthe BMS controller 366, in some embodiments, the sensor diagnosticsystem 502 may be a component of, an aspect of, or otherwiseincorporated or integrated into the BMS controller 366. Similarly, insome embodiments, the BMS controller 366 may be a component of, anaspect of, or otherwise incorporated or integrated into the sensordiagnostic system 502.

The sensor diagnostic system 502 is shown to be communicably coupled tothe building 10 (e.g., the sensor(s) 506 of the building subsystem(s)428) and the BMS controller 366. The sensor diagnostic system 502 may becommunicably coupled to the building 10 and BMS controller 366 via anycommunications protocols, devices, networks, etc. which facilitatecommunication between two or more components. In some embodiments, anycommunication between the BMS controller 366 and building subsystem(s)428 may be routed through the sensor diagnostic system 502. In otherembodiments, a subset of communication, such as communications includingsensor data, may be routed through the sensor diagnostic system 502, andother communications may be exchanged directly between the buildingsubsystem(s) 428 and BMS controller 366. In each embodiment, the sensordiagnostic system 502 may be configured to receive at least some datafrom the building subsystem(s) 428 prior to processing/analyzing/etc. bythe BMS controller 366.

The sensor diagnostic system 502 is shown to include a processingcircuit 508 including a processor 510 and memory 512. In someembodiments, the processing circuit 508 may be similar to the processingcircuit 404 described above with reference to FIG. 4 . For instance, theprocessor 510 may include aspects similar to processor 406, memory 512may include aspects similar to memory 408, and so forth.

The memory 512 is shown to include a sensor fault detector 514. Thesensor fault detector 514 may be any device(s), component(s),application(s), agent(s), etc. designed or implemented to detect oridentify faults of the sensor(s) 506. In some embodiments, the sensorfault detector 514 may be configured to determine that various sensor(s)506 are experiencing faults based on the sensor data received from thesensor(s) 506. The sensor fault detector 514 may determine that varioussensor(s) 506 are experiencing faults based on a comparison of sensordata received from the sensor(s) 506 to other sensor(s) 506 servicingthe same area or space, based on a comparison of sensor data receivedfrom the sensor(s) 506 in comparison to known, stored, etc. sensor datacorresponding to fault conditions, and so forth. In some embodiments,the sensor fault detector 514 may be incorporated into the FDD layer 414of the BMS controller 366. In some embodiments, the sensor faultdetector 514 may identify faulty sensor data using one or morerules/sub-rules. The sensor fault detector 514 may include aspectssimilar to those described with reference to U.S. Publication No.2019/0025776-A1, filed Feb. 8, 2018, and titled “BUILDING MANAGEMENTSYSTEM WITH DYNAMIC RULES WITH SUB-RULE REUSE AND EQUATION DRIVEN SMARTDIAGNOSTICS,” the contents of which are herein incorporated by referencein its entirety. While these particular embodiments and arrangements aredescribed and incorporated by reference, the sensor fault detector 514may be configured to use any number of techniques for identifying faultysensor data. Hence, the present disclosure is not limited to anyparticular arrangement of determining that the sensor data is faulty.

The memory 512 is shown to include a data classifier 516. The dataclassifier 516 may be any device(s), component(s), application(s),agent(s), etc. designed or implemented to classify sensor data from thesensor(s) 506. The data classifier 516 may be configured to classify thesensor data based on metadata for the sensor data. The metadata may beindicative of an attribute of the sensor data. For instance, themetadata may be indicative of an attribute of the sensor(s) 506 whichgenerated the sensor data (such as a location of the sensor(s) 506, aspace in which the sensor(s) 506 service, etc., a time at which thesensor data is captured or provided to the sensor diagnostic system 502,weather conditions, such as temperature, humidity, air pressure, etc. inwhich the sensor data is captured, the equipment set point, and soforth). The data classifier 516 may be configured to classify the sensordata received from the sensor(s) 506 according to the attribute(s) ofthe sensor data. In some embodiments, the data classifier 516 classifiesall sensor data received from each of the sensor(s) 506. In someembodiments, the data classifier 516 classifies sensor data which isdetermined to be “good” data (e.g., not faulty). The data classifier 516may classify the good sensor data. The data classifier 516 may beconfigured to store the good data in the historical data repository 504for subsequent use, as described in greater detail below.

As described briefly above, the system 500 is shown to include ahistorical data repository 504. The historical data repository 504 maybe or include any storage device, memory, server, database, etc.configured to store historical sensor data. The historical datarepository 504 may be configured to receive the classified sensor datafrom the data classifier 516. In some embodiments, the data classifier516 may be configured to classify the sensor data, and structure theclassified sensor data for storage in the historical data repository504. Each entry in the historical data repository 504 may be sorted,filtered, etc. according to the attributes which form the basis forclassification. As one non-limiting example, the entries may bestructured according to the structure depicted in Table 1 providedbelow.

TABLE 1 Data Structure for Historical Data Repository Entry TimestampSensor Unit OAT OAH OCC Set Sensor Data OCC Point (f) Mode

In the embodiment depicted in Table 1, the data classifier 516 may beconfigured to extract a timestamp for each sample of the sensor datafrom a respective sensor 506. The timestamp may indicate both date(e.g., MM/DD/YYYY) and time (e.g., HH:MM:SS) at which the sensor data isrecorded or sampled by the sensor 506, received by the data classifier516, etc. The timestamp may be included in the entry (e.g., asTimestamp). In embodiments where the data classifier 516 classifies allsensor data (including faulty sensor data), the entry may indicatewhether the sensor data is faulty (e.g., at Sensor Data (f)). In someembodiments, the data classifier 516 may be configured to extractoperational data (e.g., either from the metadata for the sensor data,directly from the component(s)/unit(s)/equipment, or from other datasources). The data classifier 516 may be configured to include theoperational data for the unit in each entry (e.g., Unit OCC Mode). Thedata classifier 516 may be configured to extract weather data (e.g.,from the metadata, from other sensor(s) 506, etc.). The weather data mayinclude temperature, humidity, etc. The data classifier 516 may also beconfigured to extract occupancy data (if available) corresponding to thespace in which the sensor 506 services. The data classifier 516 may beconfigured to include the weather and occupancy data in each entry(e.g., as OAT, OAH, OCC). The data classifier 516 may be configured toextract a set point value (e.g., from the metadata, from othercomponents of the system 500, etc.). The set point value may be atemperature set point, for instance, an airflow set point, etc. The dataclassifier 516 may be configured to include the set point value in eachentry (e.g., as Set Point). Lastly, the data classifier 516 may beconfigured to include the sensor reading (e.g., sensor data) in theentry (e.g., as Sensor).

Each of these cells of Table 1 may correspond to various attributes ofthe sensor data. The data classifier 516 may classify received sensordata according to these various attributes, and structure an entryaccording to the classification. The data classifier 516 may provide thestructured entry to the historical data repository 504. The historicaldata repository 504 may thus store a plurality of entries includingsensor data from various sensors 506 and attributes corresponding to thesensor data.

The data classifier 516 may be configured to classify faulty sensor datareceived from the sensor(s) 506. The data classifier 516 may beconfigured to classify the faulty sensor data to determine attributescorresponding thereto. The data classifier 516 may determine theattributes corresponding to the faulty sensor data to identify sensordata in the historical data repository 504 having similar attributes, asdescribed in greater detail below. The data classifier 516 may beconfigured to classify the faulty sensor data to determine the timestampfor the faulty sensor data, the unit operational mode, the weatherconditions, occupancy information, and/or the set point. As described ingreater detail below, the faulty sensor data may be replaced withsubstitute sensor data from the historical data repository 504. The dataclassifier 516 may classify the faulty sensor data to determineattributes corresponding thereto so that the substitute sensor datawhich is replacing the faulty sensor data has similar attribute(s) tothe faulty sensor data.

The memory 512 is shown to include a data selector 518. The dataselector 518 may be any device(s), component(s), application(s),agent(s), etc. designed or implemented to look-up, locate, identify,extract, or otherwise select substitute sensor data in the historicaldata repository 504. The data selector 518 may be configured to filterthe entries in the historical data repository 504 according to theclassification of the faulty sensor data by the data classifier 516.

Referring now to FIG. 6 and FIG. 7 , depicted is a flowchart showing anexample method 600 of selecting substitute data and an exampleenvironment 700 in which the system 500 may be implemented,respectively, according to exemplary embodiments. The method 600 isdescribed with reference to the environment 700 for purposes ofillustration. However, it is noted that the present disclosure(including the method 600) is not limited to the particular environment700.

The environment 700 shown in FIG. 7 includes various components of theHVAC subsystem 440 including a filter 702, a cooling coil 704 and asupply fan 706. Air may be drawn (e.g., along a supply vent) through thefilter 702 and across the cooling coil 704 by the supply fan 706. Thesupply fan 705 may push air into the conditioned space 708. Varioustemperature sensors 710 a-710 c may be arranged within the environment700 including a first temperature sensor 710 arranged along the supplyvent (e.g., between the supply fan 706 and an outlet to the conditionedspace 708, and a second and third temperature sensors 710 b, 701 carranged along the return vent (e.g., within the vent where air exitsthe conditioned space 708). The temperature sensor(s) 710 a-710 c maymeasure temperatures of, for instance, air that flows into theconditioned space 708, air that flows from the conditioned space 708,etc. Such measurements may be used as feedback for controlling the HVACsubsystem 440. The temperature sensor(s) 710 a-710 c may measure thetemperatures at various sample rates (e.g., once a minute, once an hour,etc.). During normal operation, in some instances, one of thetemperature sensor(s) 710 a-710 c may experience a fault. The fault maybe intermittent (e.g., one sample of sensor data is faulty, butsubsequent sensor data is good), or the fault may be persistent (e.g.,several (or all) samples of the sensor data is faulty). In the followingexample, the temperature sensor 710 b may provide faulty sensor data, asdetermined by the sensor fault detector 514.

The data classifier 516 may identify one or more attributescorresponding to the faulty sensor data from the temperature sensor 710b. For instance, the data classifier 516 may identify the timestamp,unit operation mode, weather conditions, set point, etc. correspondingto the faulty sensor data. The data classifier 516 may identify suchattributes based on the metadata for the faulty sensor data, based ondata from other components/devices within the system 500, etc. Asdescribed in greater detail below, the data selector 518 may beconfigured to select substitute data from the historical data repository504 based on the attributes corresponding to the faulty sensor data fromthe temperature sensor 710 b.

At step 602, the data selector 518 filters the entries in the historicaldata repository 504 by recent date. Specifically, the data selector 518may apply a filter to the entries to filter out older data (e.g., datafrom previous hours, days, weeks, months, etc.) from the sensor whichgenerated the faulty sensor data. As such, following step 602, theentries from the historical data repository may be those generated bythe sensor which are most recent.

At step 604, the data selector 518 filters the entries in the historicaldata repository 504 by unit operating (e.g., OCC) mode. Specifically,the data selector 518 may apply a filter to the entries to filter outentries in which the unit OCC mode is off. Hence, the remaining entriesfollowing the filter applied at step 604 include those in which the unitOCC mode is on/enabled/active/high/1/etc. Where the unit mode is off,the sensor data may not be as accurate. As such, the data selector 518may filter out data where the unit mode is off to increase the accuracyof the substitute sensor data.

At step 606, the data selector 518 filters the entries in the historicaldata repository 504 by set point. The data selector 518 may thus removeentries in the historical data repository 504 having a set point whichare not the same as (or within a threshold of, such as +/−1%, 2%, 5%,etc.) the current set point. The entries remaining following applicationof the filter at step 606 may include those having a set point which issubstantially the same as the current set point.

At step 608, the data selector 518 filters the entries in the historicaldata repository 504 by ambient temperature (OAT), ambient humidity(OAH), and/or occupancy (OCC). The data selector 518 may apply each (ora subset) of filters based on the OAT, OAH, OCC to identify entrieshaving conditions most similar to present conditions.

At step 610, the data selector 518 determines whether any of the entriesfollowing the filtering described at steps 602-608 match the attributescorresponding to the faulty sensor data from the temperature sensor 710b. In some instances, following application of each of the filtersdescribed at steps 602-608, a plurality of entries may be present in thehistorical data repository 504. In other instances, followingapplication of each of the filters described at steps 602-608, one entrymay be present in the historical data repository 504. In still otherinstances, following application of each of the filters described atsteps 602-608, no entries may be present in the historical datarepository 504. Where no entries are present in the historical datarepository 504 following application of each of the filters described atsteps 602-608, the method 600 may proceed to step 614. Where at leastone entry is present, the method 600 may proceed to step 612.

At step 612, the data selector 518 selects the substitute sensor data.In some embodiments, the data selector 518 may select the substitutesensor data from the historical data repository 504. Followingapplication of the various filter(s) described herein, at least oneattribute of the faulty sensor data may match at least one attribute ofthe substitute sensor data from the historical data repository 504.Hence, the substitute sensor data may be similar in at least someaspects to the faulty sensor data. The substitute sensor data may haveat least one attribute in common with the faulty sensor data. In someinstances, the substitute sensor data may have each attribute in commonwith the faulty sensor data. Where a plurality of entries are presentfollowing application of the filters described at steps 602-608, in someembodiments, the data selector 518 may select the most recent entry(e.g., entry having a timestamp which is closest to the timestamp forthe faulty sensor data).

At step 614, the data selector 518 refers to sensor data in thehistorical data repository 504 from the same month as the month in thetimestamp from the faulty sensor data but the previous year. In someembodiments, the data selector 518 removes all the filters applied atsteps 602-610. Following removal of all the filters previously applied,the data selector 518 may apply a filter similar to the filter appliedat step 602 to identify entries from the same month as a current month,but in a previous year (e.g., the immediately previous year, two or moreyears back, etc.). In other words, at step 614, the data selector 518expands the scope of the search for substitute sensor data which hasattribute(s) in common with the faulty sensor data. The data selector518 may refer to the same month but a previous year, as conditions ofthe building 10 may be similar to current conditions.

At step 616, the data selector 518 repeats steps 604-608. Hence, thedata selector 518 may re-apply the filters described above withreference to steps 604-608 to identify entries having at least oneattribute in common with the faulty sensor data.

Similar to step 610, at step 618, the data selector 518 determineswhether any of the entries following the filtering described at steps614-616 match the attributes corresponding to the faulty sensor datafrom the temperature sensor 710 b. In some instances, followingapplication of each of the filters described at steps 614-616, aplurality of entries may be present in the historical data repository504. In other instances, following application of each of the filtersdescribed at steps 614-616, one entry may be present in the historicaldata repository 504. In still other instances, following application ofeach of the filters described at steps 614-616, no entries may bepresent in the historical data repository 504. Where no entries arepresent in the historical data repository 504 following application ofeach of the filters described at steps 614-616, the method 600 mayproceed to step 620. Where at least one entry is present, the method 600may proceed back to step 612.

At step 620, the data selector 518 refers to sensor data in thehistorical data repository 504 from the previous year. Similar to step614, the data selector 518 may be configured to remove the filterspreviously applied and expand the scope of the search to identifyentries within the previous year. In various embodiments, the dataselector 518 may expand the scope of the search to identify entrieswithin several years.

At step 622, the data selector 518 repeats steps 604-608. Hence, thedata selector 518 may re-apply the filters described above withreference to steps 604-608 to identify entries having at least oneattribute in common with the faulty sensor data.

Similar to step 610 and step 618, at step 624, the data selector 518determines whether any of the entries following the filtering describedat steps 620-622 match the attributes corresponding to the faulty sensordata from the temperature sensor 710 b. In some instances, followingapplication of each of the filters described at steps 620-622, aplurality of entries may be present in the historical data repository504. In other instances, following application of each of the filtersdescribed at steps 620-622, one entry may be present in the historicaldata repository 504. In still other instances, following application ofeach of the filters described at steps 620-622, no entries may bepresent in the historical data repository 504. Where no entries arepresent in the historical data repository 504 following application ofeach of the filters described at steps 620-622, the method 600 mayproceed to step 626. Where at least one entry is present, the method 600may proceed to step 612.

At step 626, the data selector 518 averages senor data from similartemperature sensor(s) 710. The data selector 518 may identify a space inwhich the temperature sensor 710 services (e.g., temperature sensor 710b services the return vent for the conditioned space 708). The dataselector 518 may identify the space based on the metadata from thetemperature sensor 710, based on an identifier corresponding to thetemperature sensor 710 and corresponding data accessible by the dataselector 518 (such as a digital map or other data structure whichincludes data corresponding to a location of various sensor(s) 506within the building 10). The data selector 518 may identify othertemperature sensors 710 which service the same space (e.g., temperaturesensor 710 c also services the return vent for the conditioned space708). The data selector 518 may be configured to compute an average ofthe sensor data from the temperature sensor 710 c and other temperaturesensor(s) 710 which service the same space (e.g., an average of aplurality of samples). In instance (such as the environment 700) whereonly one other temperature sensor 710 c services the same space, thedata selector 518 may identify the sample from the other temperaturesensor 710 c. However, where a plurality of temperature sensors 710service the same space as the temperature sensor 710 which generated thefaulty sensor data, the data selector 518 may compute the average of thesensor data from the other temperature sensors 710. It is noted that, inthe environment 700, the data selector 518 may not consider data fromthe first temperature sensor 710 a, as the first temperature sensor 710a services the supply vent (which may register colder temperatures asthose registered by temperature sensors on the return vent).

While the filters described in FIG. 6 are provided herein, it is notedthat the present disclosure is not limited to the particular filters (ororder of filtering) described with reference to FIG. 6 . To thecontrary—the present disclosure contemplates variations of the filtersapplied, the order in which filter(s) are applied, etc. Hence, the dataselector 518 generally selects substitute sensor data from thehistorical data repository 504 based on a comparison of at least oneattribute of the substitute sensor data and the faulty sensor data. Thedata selector 518 may select the substitute sensor data from thehistorical data repository 504 which has at least one attribute incommon.

The memory 512 is shown to include a data replacer 520. The datareplacer 520 may be any device(s), component(s), application(s),agent(s), etc. designed or implemented to replace the faulty sensor datawith substitute sensor data selected by the data selector 518. In someembodiments, the sensor diagnostic system 502 may package sensor datafrom a plurality of sensor(s) 506 into a single packet. Hence, allsensor data received from the sensor(s) 506 may be packagedtogether—including faulty sensor data. The data replacer 520 may beconfigured to replace the faulty sensor data with the substitute sensordata identified by the data selector 518. The data replacer 520 may thusreplace faulty sensor data while maintaining “good” sensor data.

In some embodiments, the sensor diagnostic system 502 may provide,individually, samples of the sensor data. Hence, the data replacer 520may replace sensor data determined to be faulty (e.g., by the sensorfault detector 514) with the substitute sensor data. In someembodiments, the data replacer 520 may maintain the metadata for thefaulty sensor data while replacing the faulty sensor data itself withthe substitute sensor data. In other embodiments, the data replacer 520may replace the entire packet (e.g., the faulty sensor data and metadatacorresponding thereto) with the entry corresponding to the substitutesensor data.

The sensor diagnostic system 502 may be configured to provide thesubstitute sensor data to the BMS controller 366. The BMS controller 366may be configured to receive, at least, the substitute sensor data fromthe sensor diagnostic system 502. Specifically, the building subsystemintegration layer 422 of the BMS controller 366 may be configured toreceive the substitute sensor data. The BMS controller 366 may beconfigured to control various aspects and components of the buildingsubsystem 428 based on the substitute sensor data.

In some embodiments, at each iteration where the sensor(s) 506 generatefaulty sensor data, the sensor diagnostic system 502 may replace thefaulty sensor data with selected substitute sensor data. The sensordiagnostic system 502 may replace the faulty sensor data with selectedsubstitute sensor data so long as faulty sensor data is identified,until the corresponding sensor(s) 506 are replaced, until a manualoverride selection is received, etc.

Referring now to FIG. 8 , depicted is a flowchart showing an examplemethod 800 of managing sensor data, according to an exemplaryembodiment. The method 800 may be practiced by the systems, devices,components, etc. described above with reference to FIG. 1-7 . However,the present disclosure is not limited to these particular systems,devices, components

At step 802, the sensor diagnostic system 502 receives sensor data. Insome embodiments, the sensor diagnostic system 502 may receive thesensor data from a sensor 506 of a building subsystem 428 which servicesa space in the building 10. The sensor diagnostic system 502 may receivethe sensor data according to the sample rate for the sensor 506. Hence,in some embodiments, at least some of the steps described in method 800may be performed in accordance with the sample rate for the sensor 506.In such embodiments, the sensor diagnostic system 502 may identify thesample rate for the sensor 506 (e.g., based on metadata from the sensordata, based on stored information corresponding to the sensor 506,etc.). The sensor diagnostic system 502 may repeat each (or a subset) ofthe steps described herein at the identified sample rate for the sensor506.

At step 804, the sensor diagnostic system 502 determines whether thesensor data is faulty. Specifically, the sensor diagnostic system 502may determine whether the sensor data received at step 802 is faulty.The sensor diagnostic system 502 may determine whether the sensor datais faulty based, at least in part, on the sensor data itself. The sensordiagnostic system 502 may perform rule and sub-rule based analysis andapply various criterion to determine whether the sensor 506 whichprovided the sensor data received at step 802 is experiencing a fault.For instance, where the sensor data provides incoherent, impossible,impractical feedback, the sensor diagnostic system 502 may determinethat the sensor 506 is experiencing a fault (or that the sensor data isfaulty). Where the sensor data is determined to be good (e.g., notfaulty, the sensor 506 which provided the sensor data received at step802 is not experiencing a fault, etc.), the method 800 may proceed tostep 806. Where the sensor data is determined to be faulty, the method800 may proceed to step 808.

In some embodiments, where the sensor data is determined to be faulty,the sensor diagnostic system 502 may automatically deactivate thecorresponding sensor 506. The sensor diagnostic system 502 may generateand transmit a deactivation signal to the sensor 506. The sensor 506,upon receipt of the deactivation signal from the sensor diagnosticsystem 502, may automatically shut down, disable, cease transmission ofsensor data, sleep, or otherwise deactivate. The sensor 506 may remaindeactivated until repair or replacement (e.g., by a technician).

At step 808, the sensor diagnostic system 502 identifies one or moreattributes for the faulty sensor data. The sensor diagnostic system 502may identify the one or more attributes based on, for instance, metadatacorresponding to the sensor data received at step 802, based oncontextual or semantic information accessible by the sensor diagnosticsystem 502, etc. The sensor diagnostic system 502 may be configured toclassify the faulty sensor data based on the one or more attributes.Such classifications may be used for identifying substitute sensor datafor replacing the faulty sensor data.

At step 810, the sensor diagnostic system 502 selects substitute sensordata. In some embodiments, the sensor diagnostic system 502 may selectthe substitute sensor data for the sensor 506. The sensor diagnosticsystem 502 may select the substitute sensor data from a historical datarepository 504. The historical data repository may be configured tostore historical data from a plurality of sensor(s) 506. The historicaldata may include one or more attributes which define one or morecharacteristics in which the historical data was captured. Variousexamples of attributes include those shown in Table 1 shown anddescribed above. Step 810 may include at least one or more of the stepsdescribed with reference to FIG. 6 . Hence, the sensor diagnostic system502 may select substitute sensor data which has at least one attributein common (or similar to) the identified attributes for the faultysensor data (e.g., identified at step 808).

At step 812, the sensor diagnostic system 502 provides the sensor datato the BMS controller 366. Where the sensor data received at step 802 isdetermined to not be faulty (e.g., the sensor data is good), the sensordiagnostic system 502 may provide the sensor data received at step 802to the BMS controller 366. Where the sensor data received at step 802 isdetermined to be faulty, the sensor diagnostic system 502 may providethe substitute sensor data to the BMS controller 366. Hence, the sensordiagnostic system 502 may dynamically and automatically replace faultysensor data with similar substitute sensor data.

The sensor diagnostic system 502 may replace the faulty sensor data ateach sample for the sensor 506 (e.g., replaced at the identified samplerate for the sensor 506). In some embodiments, the senor diagnosticsystem 502 may receive a disable signal. The sensor diagnostic system502 may receive the disable signal from, for instance, an operatorclient device (e.g., by a corresponding operator). The operator maycontrol the operator client device to generate the disable signalresponsive to repairing the corresponding sensor 506, responsive torepeated heat or cool calls (which may indicate the substitute sensordata is insufficient for replacing the faulty sensor data), or otherreason. Responsive to the sensor diagnostic system 502 receiving thedisable signal, the sensor diagnostic system 502 may cease providing thesubstitute sensor data to the BMS controller 366. In some embodiments,the sensor diagnostic system 502 may provide the sensor data received atstep 802 responsive to receiving the disable signal (for instance, whenthe sensor 506 has been serviced/replaced). In other embodiments, thesensor diagnostic system 502 may provide an empty set or otherwiseremove (without replacing) the faulty sensor data.

Configuration of Exemplary Embodiments

As utilized herein, the terms “approximately,” “about,” “substantially”,and similar terms are intended to have a broad meaning in harmony withthe common and accepted usage by those of ordinary skill in the art towhich the subject matter of this disclosure pertains. It should beunderstood by those of skill in the art who review this disclosure thatthese terms are intended to allow a description of certain featuresdescribed and claimed without restricting the scope of these features tothe precise numerical ranges provided. Accordingly, these terms shouldbe interpreted as indicating that insubstantial or inconsequentialmodifications or alterations of the subject matter described and claimedare considered to be within the scope of the disclosure as recited inthe appended claims.

It should be noted that the term “exemplary” and variations thereof, asused herein to describe various embodiments, are intended to indicatethat such embodiments are possible examples, representations, orillustrations of possible embodiments (and such terms are not intendedto connote that such embodiments are necessarily extraordinary orsuperlative examples).

The term “coupled” and variations thereof, as used herein, means thejoining of two members directly or indirectly to one another. Suchjoining may be stationary (e.g., permanent or fixed) or moveable (e.g.,removable or releasable). Such joining may be achieved with the twomembers coupled directly to each other, with the two members coupled toeach other using a separate intervening member and any additionalintermediate members coupled with one another, or with the two memberscoupled to each other using an intervening member that is integrallyformed as a single unitary body with one of the two members. If“coupled” or variations thereof are modified by an additional term(e.g., directly coupled), the generic definition of “coupled” providedabove is modified by the plain language meaning of the additional term(e.g., “directly coupled” means the joining of two members without anyseparate intervening member), resulting in a narrower definition thanthe generic definition of “coupled” provided above. Such coupling may bemechanical, electrical, or fluidic.

The term “or,” as used herein, is used in its inclusive sense (and notin its exclusive sense) so that when used to connect a list of elements,the term “or” means one, some, or all of the elements in the list.Conjunctive language such as the phrase “at least one of X, Y, and Z,”unless specifically stated otherwise, is understood to convey that anelement may be either X, Y, Z; X and Y; X and Z; Y and Z; or X, Y, and Z(i.e., any combination of X, Y, and Z). Thus, such conjunctive languageis not generally intended to imply that certain embodiments require atleast one of X, at least one of Y, and at least one of Z to each bepresent, unless otherwise indicated.

References herein to the positions of elements (e.g., “top,” “bottom,”“above,” “below”) are merely used to describe the orientation of variouselements in the FIGURES. It should be noted that the orientation ofvarious elements may differ according to other exemplary embodiments,and that such variations are intended to be encompassed by the presentdisclosure.

Although the figures and description may illustrate a specific order ofmethod steps, the order of such steps may differ from what is depictedand described, unless specified differently above. Also, two or moresteps may be performed concurrently or with partial concurrence, unlessspecified differently above. Such variation may depend, for example, onthe software and hardware systems chosen and on designer choice. Allsuch variations are within the scope of the disclosure. Likewise,software implementations of the described methods could be accomplishedwith standard programming techniques with rule-based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps, and decision steps.

It is important to note that the construction and arrangement of theHVAC actuator and assembly thereof as shown in the various exemplaryembodiments is illustrative only. Additionally, any element disclosed inone embodiment may be incorporated or utilized with any other embodimentdisclosed herein. Although only one example of an element from oneembodiment that can be incorporated or utilized in another embodimenthas been described above, it should be appreciated that other elementsof the various embodiments may be incorporated or utilized with any ofthe other embodiments disclosed herein.

What is claimed is:
 1. A system for managing a plurality of a sensors ofa building, the system comprising: a data repository configured to storesensor data from the plurality of sensors; a building management system(BMS) controller configured to monitor or control one or more componentsof the building based on sensor data provided by the plurality ofsensors; and a sensor diagnostic system comprising one or moreprocessors and memory storing instructions that, when executed by theone or more processors, cause the one or more processors to: receive aplurality of samples of the sensor data from the plurality of sensors;classify each of the plurality of samples of the sensor data as faultyor non-faulty; generate supplemental data based on a subset of theplurality of samples of the sensor data that are classified as faultyand corresponding attributes of the subset of the plurality of samplesof the sensor data that are classified as faulty; and provide thesupplemental data to the BMS controller to monitor or control the one ormore components of the building based on the supplemental data.
 2. Thesystem of claim 1, wherein: the supplemental data comprise substitutesensor data including replacement values for the subset of the pluralityof samples of the sensor data that are classified as faulty; and the BMScontroller is configured to control the one or more components of thebuilding using the substitute sensor data in replacement of the subsetof the plurality of samples of the sensor data that are classified asfaulty.
 3. The system of claim 1, wherein: the supplemental datacomprise a number of occurrences of a fault within a time period basedon the subset of the plurality of samples of the sensor data that areclassified as faulty; and the BMS controller is configured to generate auser interface to monitor the one or more components of the buildingusing the supplemental data to quantify the number of occurrences of thefault within the time period.
 4. The system of claim 1, wherein thecorresponding attributes comprise a set point for the one or morecomponents of the building or a space of the building monitored orcontrolled using the plurality of samples of the sensor data from theplurality of sensors.
 5. The system of claim 1, wherein: thesupplemental data comprise calculated or aggregated values based on theattributes of the subset of the plurality of samples of the sensor datathat are classified as faulty; and the attributes indicate at least oneof identities of the plurality of sensors, equipment associated with theplurality of sensors, spaces associated with the plurality of sensors,or times at which the plurality of samples are measured by the pluralityof sensors.
 6. The system of claim 1, wherein the instructions furthercause the one or more processors to deactivate a first sensor of theplurality of sensors responsive to detecting a fault based on the sensordata provided by the first sensor.
 7. The system of claim 1, wherein theBMS controller is configured to adjust an operation of the one or morecomponents of the building to reduce the subset of the plurality ofsamples of the sensor data that are classified as faulty.
 8. A sensordiagnostic system for a plurality of sensors of a building, the systemcomprising one or more processors and memory storing instructions that,when executed by the one or more processors, cause the one or moreprocessors to: receive a plurality of samples of sensor data from theplurality of sensors; classify each of the plurality of samples of thesensor data as faulty or non-faulty; generate supplemental data based ona subset of the plurality of samples of the sensor data that areclassified as faulty and corresponding attributes of the subset of theplurality of samples of the sensor data that are classified as faulty;and provide the supplemental data to a controller to monitor or controlone or more components of the building based on the supplemental data.9. The system of claim 8, wherein: the supplemental data comprisesubstitute sensor data including replacement values for the subset ofthe plurality of samples of the sensor data that are classified asfaulty; and the controller is configured to control the one or morecomponents of the building using the substitute sensor data inreplacement of the subset of the plurality of samples of the sensor datathat are classified as faulty.
 10. The system of claim 8, wherein: thesupplemental data comprise a number of occurrences of a fault within atime period based on the subset of the plurality of samples of thesensor data that are classified as faulty; and the controller isconfigured to generate a user interface to monitor the one or morecomponents of the building using the supplemental data to quantify thenumber of occurrences of the fault within the time period.
 11. Thesystem of claim 8, wherein the corresponding attributes comprise a setpoint for the one or more components of the building or a space of thebuilding monitored or controlled using the plurality of samples of thesensor data from the plurality of sensors.
 12. The system of claim 8,wherein: the supplemental data comprise calculated or aggregated valuesbased on the attributes of the subset of the plurality of samples of thesensor data that are classified as faulty; and the attributes indicateat least one of identities of the plurality of sensors, equipmentassociated with the plurality of sensors, spaces associated with theplurality of sensors, or times at which the plurality of samples aremeasured by the plurality of sensors.
 13. The system of claim 8, whereinthe instructions further cause the one or more processors to deactivatea first sensor of the plurality of sensors responsive to detecting afault based on the sensor data provided by the first sensor.
 14. Thesystem of claim 8, wherein the controller is configured to adjust anoperation of the one or more components of the building to reduce thesubset of the plurality of samples of the sensor data that areclassified as faulty.
 15. A method for managing a plurality of sensorsof a building, the method comprising: receiving a plurality of samplesof sensor data from the plurality of sensors; classifying each of theplurality of samples of the sensor data as faulty or non-faulty;generating supplemental data based on a subset of the plurality ofsamples of the sensor data that are classified as faulty andcorresponding attributes of the subset of the plurality of samples ofthe sensor data that are classified as faulty; and providing thesupplemental data to a controller to monitor or control one or morecomponents of the building based on the supplemental data.
 16. Themethod of claim 15, wherein: the supplemental data comprise substitutesensor data including replacement values for the subset of the pluralityof samples of the sensor data that are classified as faulty; and themethod comprises controlling the one or more components of the buildingusing the substitute sensor data in replacement of the subset of theplurality of samples of the sensor data that are classified as faulty.17. The method of claim 15, wherein: the supplemental data comprise anumber of occurrences of a fault within a time period based on thesubset of the plurality of samples of the sensor data that areclassified as faulty; and the method comprises generating a userinterface to monitor the one or more components of the building usingthe supplemental data to quantify the number of occurrences of the faultwithin the time period.
 18. The method of claim 15, wherein thecorresponding attributes comprise a set point for the one or morecomponents of the building or a space of the building monitored orcontrolled using the plurality of samples of the sensor data from theplurality of sensors.
 19. The method of claim 15, wherein: thesupplemental data comprise calculated or aggregated values based on theattributes of the subset of the plurality of samples of the sensor datathat are classified as faulty; and the attributes indicate at least oneof identities of the plurality of sensors, equipment associated with theplurality of sensors, spaces associated with the plurality of sensors,or times at which the plurality of samples are measured by the pluralityof sensors.
 20. The method of claim 15, comprising at least one of:deactivating a first sensor of the plurality of sensors responsive todetecting a fault based on the sensor data provided by the first sensor;or adjusting an operation of the one or more components of the buildingto reduce the subset of the plurality of samples of the sensor data thatare classified as faulty.